"Is Not" Conditions on Custom Fields Now Produce Correct List Results

Lists

An issue was resolved where using two or more "Is Not" conditions on custom fields within the same AND condition group in the List Builder produced incorrect results, causing records that should have been excluded to appear as list members.

What This Fix Means:

AND-combined "Is Not" conditions on custom fields now behave exactly as configured. Previously, records failing to meet exclusion criteria were silently passed through, pulling them into automations they were never intended for, potentially triggering unwanted communications, status changes, or workflow steps on the wrong records. This fix restores confidence in exclusion logic and ensures list membership accurately reflects configured criteria.